plone / jenkins.plone.org

https://jenkins.plone.org settings docs at
http://jenkinsploneorg.readthedocs.org/en/latest/
9 stars 1 forks source link

PR result on 6.1 is not correct #373

Open mauritsvanrees opened 2 weeks ago

mauritsvanrees commented 2 weeks ago

See https://github.com/plone/buildout.coredev/pull/961#issuecomment-2431398162. Success is reported in the PR, but the 3.12 job actually failed. The last lines of the console output are:

Also teardown failed:
Error: Tried to take screenshot, but no page was open.

/tmp/jenkins13979994533636698782.sh: line 43: 1758725 Killed                  bin/test --all --xml . -t ONLYROBOT
+ return_code=137
+ '[' 137 = all_right ']'
+ python templates/pr-update-status-py3.py
+ exit 137
Build step 'Execute shell' marked build as failure
Recording test results
[Checks API] No suitable checks publisher found.
Robot results publisher started...
INFO: Checking test criticality is deprecated and will be dropped in a future release!
-Parsing output xml:
Done!
-Copying log files to build dir:
Done!
-Assigning results to build:
Done!
-Checking thresholds:
Done!
Done publishing Robot results.
Email was triggered for: Always
Sending email for trigger: Always
Sending email to: gilforcada@gmail.com
Finished: FAILURE

Not sure what is going on there.

gforcada commented 2 weeks ago

Maybe the logic we have on the pr-update-status-py3.py is not good enough?

https://github.com/plone/buildout.coredev/blob/6.1/templates/pr-update-status-py3.py#L35-L56