nodejs / nodejs/build

Seemingly random compilation failures

Open
#4,082 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jinja
Stars
541
Forks
185
Avg merge
22h 15m
Merged PRs (30d)
4

Description

From @tniessen via https://openjs-foundation.slack.com/archives/C03BJP63CH0/p1747507311133849

Has anyone else seen some unexpected compilation failures during Jenkins CI runs? For example, this run failed with C++ compiler errors even though the PR being tested does not touch C++ at all, and I am pretty sure I saw some similar errors over the last few days: https://ci.nodejs.org/job/node-test-commit-linux-containered/50707/

e.g. https://ci.nodejs.org/job/node-test-commit-linux-containered/50707/nodes=ubuntu2204_sharedlibs_shared_x64/console

19:19:39 In file included from ../deps/ada/ada.cpp:3:
19:19:39 ../deps/ada/ada.h: In member function 'constexpr std::string_view ada::url::get_pathname() const':
19:19:39 ../deps/ada/ada.h:6621:10: error: call to non-'constexpr' function 'std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::operator std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::__sv_type() const [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>; std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::__sv_type = std::basic_string_view<char>]'
19:19:39  6621 |   return path;
19:19:39       |          ^~~~
19:19:39 In file included from /usr/include/c++/11/string:55,
19:19:39                  from ../deps/ada/ada.h:20,
19:19:39                  from ../deps/ada/ada.cpp:3:
19:19:39 /usr/include/c++/11/bits/basic_string.h:806:7: note: 'std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::operator std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::__sv_type() const [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>; std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::__sv_type = std::basic_string_view<char>]' declared here
19:19:39   806 |       operator __sv_type() const noexcept
19:19:39       |       ^~~~~~~~
...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Jenkins run 50707 and its ubuntu2204_sharedlibs_shared_x64 console output, then compare it with the similar failures mentioned in the issue. Trace why unrelated C++ compilation is occurring during CI and verify the cause across subsequent runs; done means the intermittent failures are explained and the affected CI path no longer fails unexpectedly.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
build-system, ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.