Started 26 days ago
Took 2 hr 6 min on green-dragon-18

Failed Build rL:372458 - C:372462 - #706 (Sep 21, 2019 1:05:23 AM)

  • : 372458
  • : 372462
  • : 372461
  • : 364589
  • : 372433
  • : 372242
  • : 372445
  1. Attempt to fix a windows buildbot failure (detail/ViewSVN)
    by szelethus
  2. Add __lsan::ScopedInterceptorDisabler for strerror(3)

    strerror(3) on NetBSD uses internally TSD with a destructor that is never
    fired for exit(3). It's correctly called for pthread_exit(3) scenarios.

    This is a case when a leak on exit(3) is expected, unavoidable and harmless.

    Reviewers: joerg, vitalybuka, dvyukov, mgorny

    Reviewed By: vitalybuka

    Subscribers: dmgreen, kristof.beyls, jfb, llvm-commits, #sanitizers

    Tags: #sanitizers, #llvm

    Differential Revision: (detail/ViewSVN)
    by kamil
  3. Avoid memory leak in ASan test

    Add missing free(3) for the malloc(3) call.

    Detected on NetBSD with LSan.

    Reviewers: joerg, mgorny, vitalybuka, dvyukov

    Reviewed By: vitalybuka

    Subscribers: llvm-commits, #sanitizers

    Tags: #sanitizers, #llvm

    Differential Revision: (detail/ViewSVN)
    by kamil
  4. Stop tracking atexit/__cxa_atexit/pthread_atfork allocations in LSan/NetBSD

    The atexit(3) and __cxa_atexit() calls allocate internally memory and free on exit,
    after executing all callback. This causes false positives as DoLeakCheck() is called
    from the atexit handler. In the LSan/ASan tests there are strict checks triggering
    false positives here.

    Intercept all atexit(3) and __cxa_atexit() calls and disable LSan when calling the
    real functions.

    Stop tracing allocations in pthread_atfork(3) funtions, as there are performed
    internal allocations that are not freed for the time of running StopTheWorld()
    code. This avoids false-positives.

    The same changes have to be replicated in the ASan and LSan runtime.

    Non-NetBSD OSs are not tested and this code is restricted to NetBSD only.

    Reviewers: dvyukov, joerg, mgorny, vitalybuka, eugenis

    Reviewed By: vitalybuka

    Subscribers: jfb, llvm-commits, #sanitizers

    Tags: #sanitizers, #llvm

    Differential Revision: (detail/ViewSVN)
    by kamil
  5. [X86] Use sse_load_f32/f64 and timm in patterns for memory form of vgetmantss/sd.

    Previously we only matched scalar_to_vector and scalar load, but
    we should be able to narrow a vector load or match vzload.

    Also need to match TargetConstant instead of Constant. The register
    patterns were previously updated, but not the memory patterns. (detail/ViewSVN)
    by ctopper
  6. [X86] Add test case to show failure to fold load with getmantss due to isel pattern looking for Constant instead of TargetConstant

    The intrinsic has an immarg so its gets created with a TargetConstant
    instead of a Constant after r372338. The isel pattern was only
    updated for the register form, but not the memory form. (detail/ViewSVN)
    by ctopper

Started by an SCM change (4 times)

This run spent:

  • 1 hr 18 min waiting;
  • 2 hr 6 min build duration;
  • 3 hr 24 min total from scheduled to completion.
LLVM/Clang Warnings: 0 warnings.

Identified problems

Ninja target failed

Below is a link to the first failed ninja target.
Indication 1

Missing test results

The test result file Jenkins is looking for does not exist after the build.
Indication 2