[DTrace-devel] [oracle/dtrace-utils] fdcab0: test: Add trigger for more predictable run time

Alan Maguire noreply at github.com
Thu Sep 18 00:37:58 UTC 2025


  Branch: refs/heads/dev-queue
  Home:   https://github.com/oracle/dtrace-utils
  Commit: fdcab087f71aba66a710bcdc6807c65bf13354ac
      https://github.com/oracle/dtrace-utils/commit/fdcab087f71aba66a710bcdc6807c65bf13354ac
  Author: Eugene Loh <eugene.loh at oracle.com>
  Date:   2025-09-17 (Wed, 17 Sep 2025)

  Changed paths:
    M test/unittest/error/tst.argv-corruption-by-error.d

  Log Message:
  -----------
  test: Add trigger for more predictable run time

The test had no trigger and so waited haphazardly for the write:entry
probe to fire.  This typically worked, but led to variable run times
and even, though rarely, a test timeout and failure.

Add a trigger for more reproducible and typically shorter run times.

Signed-off-by: Eugene Loh <eugene.loh at oracle.com>
Reviewed-by: Kris Van Hees <kris.van.hees at oracle.com>


  Commit: bb37d5219f76c58e5dbcc9a02054066320ae883d
      https://github.com/oracle/dtrace-utils/commit/bb37d5219f76c58e5dbcc9a02054066320ae883d
  Author: Elena Zannoni <elena.zannoni at oracle.com>
  Date:   2025-09-17 (Wed, 17 Sep 2025)

  Changed paths:
    M dtrace.spec

  Log Message:
  -----------
  Make sure the doc dir is cleaned up on RPM uninstall

Add to the RPM file list the entire dtrace doc directory, not just its
contents.

Signed-off-by: Elena Zannoni <elena.zannoni at oracle.com>
Reviewed-by: Nick Alcock <nick.alcock at oracle.com>


  Commit: 7b3a44719d539044b8508b7d8bebcbef011059ac
      https://github.com/oracle/dtrace-utils/commit/7b3a44719d539044b8508b7d8bebcbef011059ac
  Author: Alan Maguire <alan.maguire at oracle.com>
  Date:   2025-09-17 (Wed, 17 Sep 2025)

  Changed paths:
    M libdtrace/dt_grammar.y
    A test/unittest/enum/err.EnumMissingSymbol-1.d
    A test/unittest/enum/err.EnumMissingSymbol-2.d
    A test/unittest/enum/err.EnumMissingSymbol-3.d
    A test/unittest/enum/tst.EnumTrailingComma.d

  Log Message:
  -----------
  enum: support declarations with a trailing comma

When doing python tracing, it was recently observed that #include'ing
a file with enum declarations with trailing commas fails; this is
due to the D grammar being strict about the last enumerator value
not having a trailing comma.  So

enum foo {
	BAR,
	BAZ
};

is permitted, but

enum foo {
	BAR,
	BAZ,
};

is not.  The latter pattern is used quite frequently in #include
files, especially where conditional compilation of some enum
values is done.

Relax this constraint and add a test to validate that D compilation
succeeds with the trailing comma in an enum declaration.

Signed-off-by: Alan Maguire <alan.maguire at oracle.com>
Reviewed-by: Kris Van Hees <kris.van.hees at oracle.com>


Compare: https://github.com/oracle/dtrace-utils/compare/7147201e20d6...7b3a44719d53

To unsubscribe from these emails, change your notification settings at https://github.com/oracle/dtrace-utils/settings/notifications



More information about the DTrace-devel mailing list