4.40 I-Build: I20260504-1800 - BUILD FAILED -- Forbidden Jenkins API access

[HannesWell]

The latest I-build failed with

+ curl --fail https://ci.eclipse.org/releng/job/Builds/job/I-build-4.40/94//wfapi/describe
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 403

I verified that this is a permanent issue when accessing the wfapi from within a job:
https://ci.eclipse.org/releng/job/Builds/job/I-build-4.40/94//wfapi/describe

Interestingly I can access the URL without problems from a browser, even if logged out from the RelEng JIPP.

This is probably a consequence of

• eclipse-cbi/jiro@5fa6391

I'll ask the IT team for guidance.

[HannesWell]

I'll ask the IT team for guidance.

Created https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7456

[HannesWell]

Because the issue is not yet resolved I replayed the latest I-build with disabled fetch of build console log to at least have a successful build.
The I-build tests will probably also fail eventually when trying to report their results to the build website, but the test results should still be visible in the Jenkins UI.

[laeubi]

Interestingly I can access the URL without problems from a browser, even if logged out from the RelEng JIPP.

Are you sure? I only get a login page when I open it in a private browser tab.

[HeikoKlare]

Interestingly I can access the URL without problems from a browser, even if logged out from the RelEng JIPP.

Are you sure? I only get a login page when I open it in a private browser tab.

I also tried with a private browser tab and still can access the page without logging in. Interesting.

I just took a look at today's I-Build test results. Since they are not reported to the website, here is a short summary so that not everyone has to check no their own:

• Linux tests are without failures
• macOS aarch64 has the known failure of PartOnTopManagerTest.test_PlaceholderOnTopStackSwitch
• macOS x86 suffers from: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7455
• Windows tests timed out

[HannesWell]

Tonight’s I-build is expected to be successful again with

• [Build] Autenticate access to Jenkins API in build #3808
• https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7456

[HannesWell]

The I-build is working fine again.

• Windows tests timed out

This was also fixed via: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7465
The Windows-tests now completed within 4h10min.

[HeikoKlare]

Thank you, @HannesWell, for taking care of this! 🥇

[vogella]

The smoke test is still instable. Not sure what this is but I don't remember that it ever was successful. Is there another ticket to follow for this test?

[HeikoKlare]

I don't know about a ticket for the smoke tests. You can find the information about the job and the failures in the according Jenkins job: https://ci.eclipse.org/releng/job/AutomatedTests/job/smokeTests/

You see that like every second smoke tests execution fails because of: org.eclipse.ui.tests.concurrency.SyncExecWhileUIThreadWaitsForLock.testDeadlock